Installation Note 56231: Failures occur during configuration of the SAS® Detail Data Store for Banking 4.9 hot fix
 |  |  |  |  |
When you apply hot fixes to SAS Detail Data Store for Banking 4.9, failures might occur under the following conditions.
- The script is interrupted for any reason and stops running. If the script is partially completed, it can be rerun in its entirety. The script skips individual changes that are already completed.
- Multiple library references (librefs) named DDS are found in your metadata. Note that this is the actual libref, not the SAS metadata name for the library. If multiple librefs named DDS are found registered in SAS metadata by the script, you can temporarily rename the other DDS librefs to another name and then rerun the script. (Confirm impact before the temporary rename.) Afterward, if desired, rename the DDS librefs to their previous names.
- Your DDS libref is named something other than DDS. The overall process requires the libref to be named DDS. If the name is not DDS, you can temporarily rename it and then rename it back. (Confirm impact before the rename.)
Errors You Might See in the SAS Log under These Conditions
The included hotfix file bdds_datachg_library_parms.sas could not be found.
If the downloaded scripts provided with the hot fix are not in the file path parameter passed to the overall script, the process fails.
ERROR: Library_parms did not execute correctly. Correct and rerun.
After executing the bdds_datachg_library_parms.sas script, the libref did not come through correctly. This issue can occur if there are multiple librefs by the same name (DDS) or no DDS libref was found. Or, alternatively, if the path, engine, schema, or authdomain are not set correctly. The LIBNAME statement is built from the SAS metadata on the library. Make the correction to that SAS metadata and rerun this hot fix.
ERROR: Library_parms did not execute correctly. Correct and rerun.
When the script checks the SAS metadata, if duplicates are found, then this message is displayed and the process stops.
ERROR: Duplicate DDS libraries found in SAS metadata. Please check only one library and no other dds libraries are assigned.
If the DDS libref in SAS metadata is not for a SAS or Oracle library, then the following message is produced.
ERROR: Library requires SAS or Oracle DDS libref.
When the script checks whether the library exists, the code allocates the library based on the SAS metadata properties. If the library does not allocate, then this message is received.
ERROR: dds Library does not exist. Process ending.
The hot fix primary script, bdds_datachg_overall_script.sas, includes a passed-in parameter for the path where the scripts are downloaded. If the execution script does not exist in that path, then an error like the following is generated, where xyz represents the path. In this case, you need to correct the path in the script macro call section and rerun.
ERROR: Script files are not available in the provided path xyz. Please review and correct.
What To Do
If you encounter any of these situations during any application of SAS Detail Data Store for Banking 4.9 hot fixes, correct the libref problem by removing the multiple librefs or by ensuring that your DDS libref is named DDS. Then follow the steps below to fix the errors and complete hot fix deployment.
- Start SAS using the SAS Config SASApp .bat or .sh file, logging in as the data administrator.
The user ID must have access to the SAS metadata for SAS Detail Data Store for Banking 4.9. By using the data administrator login, the scripts execute with no prompting for user ID and password because it uses the authdomain for authentication. You can run the script in the SAS Program Editor using Base SAS® with the metadata server (see examples below), SAS® Enterprise Guide®, or the code section in SAS® Data Integration Studio. - In a Windows operating environment: SASConfig\sever-content-name\sas.bat
For example: C:\SAS\Config\Lev1\SASApp\sas.bat - In a UNIX operating environment: SASConfig/sever-content-name/sas.sh
For example: /SAS/ - Copy the \upgrade\ddl\bdds_datachg_overall_script.sas into your SAS session. The path where your hot fix scripts were installed should be identified in the t_fileloc= in the macro call. If this path is incorrect or missing, it must to be corrected or added as needed. Then execute, review log, and confirm success.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Detail Data Store for Banking | Microsoft® Windows® for x64 | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 |
| Microsoft Windows 8 Enterprise 32-bit | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8 Enterprise x64 | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8 Pro 32-bit | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8 Pro x64 | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Enterprise 32-bit | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Enterprise x64 | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Pro | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Pro 32-bit | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2008 | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2008 R2 | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2008 for x64 | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2012 Datacenter | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2012 R2 Datacenter | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2012 R2 Std | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2012 Std | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Enterprise 32 bit | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Enterprise x64 | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Home Premium 32 bit | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Home Premium x64 | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Professional 32 bit | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Professional x64 | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Ultimate 32 bit | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Windows 7 Ultimate x64 | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| 64-bit Enabled AIX | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| 64-bit Enabled Solaris | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| HP-UX IPF | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Linux for x64 | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
| Solaris for x64 | 4.9 | 5.1 | 9.4 TS1M3 | 9.4 TS1M3 | ||
A fix for this issue for SAS Detail Data Store for Banking 4.9 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/U42.html#56231| Type: | Installation Note |
| Priority: | high |
| Date Modified: | 2015-08-19 15:36:01 |
| Date Created: | 2015-07-21 14:01:26 |